Update vitest 2.1.2 → 2.1.3 (patch) #141
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ vitest (2.1.2 → 2.1.3) · Repo
Release Notes
2.1.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 36 commits:
chore: release v2.1.3
docs: update invalid link (#6698)
test: use list cli args from `test.each` (#6694)
docs: bench `Options` type add `throws` description (#6695)
fix: fix error diff of `toBeNaN, toBeUndefined, toBeNull, toBeTruthy, toBeFalsy` (#6697)
fix(runner): ensure sequential suite overrides sequence.concurrent (#6653)
fix(vitest): use `fast-glob` instead of `tinyglobby` in Vitest (#6688)
docs: mention that the browser mode uses 63315 port (#6691)
fix(browser): don't override the esbuild option in the browser mode (#6692)
fix(vitest): always inline setup files (#6689)
fix(vitest): show rollup error details as test error (#6686)
fix(browser): use `/mockServiceWorker.js` instead of `/__vitest_msw__` (#6687)
refactor(coverage): move re-usable parts to base provider (#6665)
docs: update the default `browser.provider` (#6673)
perf: reuse full name in reported tasks, update generator types (#6666)
docs: update workspace.md (#6664)
chore: never open a testing tab when running tests
chore(deps): update dependency rollup to v4.22.4 [security] (#6657)
chore(deps): update dependency micromatch to v4.0.8 [security] (#6656)
chore: make Vitest monorepo work with the vscode extension (#6658)
chore: fix `@vitest/ui` overrides (#6655)
fix(browser): not.toBeInTheDocument works with locators API (#6634)
fix(vitest): fix `<empty line>` logs when interleaving `console.log/error` (#6644)
docs: add VoidZero as special sponsor (#6639)
fix(vitest): deprecate old task types and node-reliant types (#6632)
chore: update lit example to use the new locators API (#6628)
fix(vitest): don't hang with maxConcurrency 0 (#6627)
docs: update examples links (#6631)
fix(vitest): deprecate UserConfig in favor of ViteUserConfig (#6626)
refactor: remove jsx examples in favour of browser examples (#6630)
fix(browser): provide aria role intellisense (#6629)
fix(mocker): specify correct spy dependency
chore: remove unused code (#6625)
test: refactor browser test utils (#6624)
fix(web-worker): share mocker with main executor (#6623)
fix(expect): preserve prototype in `toMatchObject` diff (#6620)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands